Skip to content

bold text in immutable-releases.md#43716

Open
dangbert wants to merge 1 commit intogithub:mainfrom
dangbert:main
Open

bold text in immutable-releases.md#43716
dangbert wants to merge 1 commit intogithub:mainfrom
dangbert:main

Conversation

@dangbert
Copy link
Copy Markdown

@dangbert dangbert commented Apr 7, 2026

Why:

Closes: #43715

What's being changed (if available, include any code snippets, screenshots, or gifs):

Make important text bold so it's harder to overlook.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
code-security/concepts/supply-chain-security/immutable-releases.md fpt
ghec
ghes
fpt
ghec
ghes

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Apr 7, 2026
@Sharra-writes
Copy link
Copy Markdown
Contributor

Sharra-writes commented Apr 10, 2026

@dangbert This doesn't fit within our style guide, however we are moving away from quotes for important items and towards putting them in bold, so this would be acceptable:

If a release is immutable, you will see {% octicon "lock" aria-hidden="true" %} Immutable below the title on the release page.

If you don't think that's sufficient, I really don't like the placement of that callout. Think of text formatting as a means of directing attention. If you direct attention somewhere with a callout, you're basically taking it away from somewhere else, and that "somewhere else" is usually the area immediately following the place where you've directed the attention. That's fine if there's a bunch of text afterward to remind the reader there's more to read, but when you follow a callout with one line of text and then a heading for a new section, that one line of text is going to get lost. I would rather see the callout at the end of the section if there's nowhere further up the section where it makes sense.

But even if the callout gets moved, "Immutable" should still be bolded, because that's what we're doing now.

@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team code security Content related to code security and removed triage Do not begin working on this issue until triaged by the team labels Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

code security Content related to code security content This issue or pull request belongs to the Docs Content team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document how to check if a release is immutable (as a user)

2 participants